Fix(Core): Optimize container loading when there are a large number of entities#1187
Merged
Fix(Core): Optimize container loading when there are a large number of entities#1187
Conversation
stonebuzz
changed the title
Rom1-B
approved these changes
Apr 29, 2026
Contributor
Author
|
validated by customer |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…f entities
Checklist before requesting a review
Please delete options that are not relevant.
Description
A user with nearly 5,000 entities is experiencing slowness when opening a ticket containing a container.
They are using a tree view with recursive mode enabled.
Currently, the plugin adds a WHERE clause on entities using all the user’s entities (
glpi_active_entities), which significantly impacts performance.The logic used to verify whether access to the container is authorized has been moved further downstream in order to lighten the SQL query.
It now relies on
Session::haveAccessToEntity.Screenshots (if appropriate):